SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>ARCNET</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">ARCNET</span></span>

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style>

<p><b>Attached Resource Computer NETwork</b> (<b>ARCNET</b> or <b>ARCnet</b>) is a <a href="Communications_protocol" class="mw-redirect" title="Communications protocol">communications protocol</a> for <a href="Local_area_network" title="Local area network">local area networks</a>.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> ARCNET was the first widely available <a href="Computer_network" title="Computer network">networking</a> system for <a href="Microcomputer" title="Microcomputer">microcomputers</a> and it became popular in the 1980s for office automation tasks. It was later applied to <a href="Embedded_system" title="Embedded system">embedded systems</a> where certain features of the protocol are especially useful.

</p>

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

<div class="mw-heading mw-heading3"><h3 id="Development">Development</h3></div>

<p>ARCNET was developed by principal development engineer <a href="John_Murphy_(engineer)" title="John Murphy (engineer)">John Murphy</a>, at <a href="Datapoint" title="Datapoint">Datapoint</a> Corporation in 1976 under <a href="Victor_Poor" title="Victor Poor">Victor Poor</a>, and announced in 1977.<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> It was originally developed to connect groups of their <a href="Datapoint_2200" title="Datapoint 2200">Datapoint 2200</a> terminals to talk to a shared 8" <a href="Floppy_disk" title="Floppy disk">floppy disk</a> system. It was the first loosely coupled LAN-based clustering system, making no assumptions about the <i>type</i> of computers that would be connected. This was in contrast to contemporary larger and more expensive computer systems such as <a href="DECnet" title="DECnet">DECnet</a> or IBM's <a href="Systems_Network_Architecture" title="Systems Network Architecture">SNA</a>, where a homogeneous group of similar or proprietary computers were connected as a <a href="VMScluster" title="VMScluster">cluster</a>.

</p><p>The token-passing bus protocol of that I/O device-sharing network was subsequently applied to allowing processing nodes to communicate with each other for file-serving and computing scalability purposes. An application could be developed in DATABUS, Datapoint's proprietary <a href="COBOL" title="COBOL">COBOL</a>-like language, and deployed on a single computer with dumb terminals. When the number of users outgrew the capacity of the original computer, additional 'compute' resource computers could be attached via ARCNET to run the same applications and access the same data. If more storage was needed, additional disk resource computers could also be attached. This incremental approach broke new ground and by the end of the 1970s (before the first <a href="IBM_PC" class="mw-redirect" title="IBM PC">IBM PC</a> was announced in 1981), over ten thousand ARCNET LAN installations were in commercial use around the world while Datapoint had become a Fortune 500 company. As microcomputers took over the industry, well-proven and reliable ARCNET was also offered as an inexpensive LAN for these machines.

</p>

<div class="mw-heading mw-heading3"><h3 id="Market">Market</h3></div>

<p>ARCNET remained proprietary until the early-to-mid 1980s. This did not cause concern at the time, as most network architectures were proprietary. The move to non-proprietary, open systems began as a response to the dominance of <a href="International_Business_Machines" class="mw-redirect" title="International Business Machines">International Business Machines</a> (IBM) and its <a href="Systems_Network_Architecture" title="Systems Network Architecture">Systems Network Architecture</a> (SNA). In 1979, the Open Systems Interconnection Reference Model (<a href="OSI_model" title="OSI model">OSI model</a>) was published. Then, in 1980, Digital, Intel and Xerox (the DIX consortium) published an <a href="Open_standard" title="Open standard">open standard</a> for <a href="Ethernet" title="Ethernet">Ethernet</a> that was soon adopted as the basis of standardization by the IEEE and the ISO. IBM responded by proposing <a href="Token_Ring" title="Token Ring">Token Ring</a> as an alternative to Ethernet but kept such tight control over standardization that competitors were wary of using it. ARCNET was less expensive than either of these, was more reliable, more flexible and, by the late 1980s, had a market share about equal to that of Ethernet. <a href="RadioShack" title="RadioShack">Tandy/Radio Shack</a> offered ARCNET as an application and file sharing medium for their <a href="TRS-80_Model_II" title="TRS-80 Model II">TRS-80 Model II</a>, <a href="TRS-80_Model_12" class="mw-redirect" title="TRS-80 Model 12">Model 12</a>, <a href="TRS-80_Model_16" class="mw-redirect" title="TRS-80 Model 16">Model 16</a>, <a href="Tandy_6000" class="mw-redirect" title="Tandy 6000">Tandy 6000</a>, <a href="Tandy_2000" title="Tandy 2000">Tandy 2000</a>, <a href="Tandy_1000" title="Tandy 1000">Tandy 1000</a> and Tandy 1200 computer models. There were also hooks in the <a href="TRS-80_Model_4" title="TRS-80 Model 4">Model 4P</a>'s ROM to boot from an ARCNET network.<sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup>

</p><p>Ethernet became much more attractive when it moved from co-axial cable to <a href="Ethernet_over_twisted_pair" title="Ethernet over twisted pair">twisted pair</a> and an "interconnected stars" cabling topology based on active <a href="Ethernet_hub" title="Ethernet hub">hubs</a>. Easier cabling, combined with the greater raw speed of Ethernet (<span class="nowrap">10 Mbit/s</span> versus <span class="nowrap">2.5 Mbit/s</span> for ARCnet) helped to increase Ethernet's demand. As more companies entered the market, the price of Ethernet started to fall while ARCNET and Token Ring volumes tapered off.

</p>

<div class="mw-heading mw-heading3"><h3 id="ARCnet_Plus_and_decline">ARCnet Plus and decline</h3></div>

<p>In response to greater bandwidth needs, and the challenge of Ethernet, a new standard called ARCnet Plus was developed by Datapoint and introduced in 1992. ARCnet Plus ran at <span class="nowrap">20 Mbit/s</span> and was backward-compatible with original ARCnet equipment. However, by the time ARCnet Plus products were ready for the market, Ethernet had captured the majority of the network market and there was little incentive for users to move back to ARCnet. As a result, very few ARCnet Plus products were ever produced. Those that were built, mainly by Datapoint, were expensive and hard to find.

</p><p>ARCNET was eventually standardized as <a href="American_National_Standards_Institute" title="American National Standards Institute">ANSI</a> ARCNET 878.1. It appears this was when the name changed from ARCnet to ARCNET. Other companies entered the market, notably Standard Microsystems who produced systems based on a single <a href="Very-large-scale_integration" title="Very-large-scale integration">VLSI</a> chip, originally developed as custom LSI for Datapoint, but later made available by Standard Microsystems to other customers. Datapoint eventually found itself in financial trouble and moved into video conferencing then and later to custom programming in the embedded market.

</p><p>Even though ARCNET is now rarely used for new general networks, the diminishing <a href="Installed_base" title="Installed base">installed base</a> still requires support and it retains a niche in industrial control.<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Description">Description</h2></div>

<p>Original ARCNET used RG-62/U <a href="Coaxial_cable" title="Coaxial cable">coaxial cable</a> of <span class="nowrap">93 <a href="Ohm" title="Ohm">Ω</a></span> <a href="Characteristic_impedance" title="Characteristic impedance">impedance</a> and either passive or active <a href="Ethernet_hub" title="Ethernet hub">hubs</a> in a star-wired <a href="Bus_(computing)" title="Bus (computing)">bus</a> topology. At the time of its greatest popularity, this was a significant advantage of ARCNET over Ethernet. A star-wired bus was much easier to build, expand and maintain than the clumsy linear bus Ethernet of the time. The "interconnected stars" cabling topology made it easy to add and remove nodes without taking down the whole network, and much easier to diagnose and isolate failures within a complex LAN.

</p><p>Another significant advantage ARCNET had over Ethernet was cable distance. ARCNET coax cable runs could extend 610 m (2,000 ft) between active hubs or between an active hub and an end node, while the <a href="RG-58" title="RG-58">RG-58</a> (50Ω) 'thin' Ethernet most widely used at that time was limited to a maximum run of 185 m (607 ft) from end to end.<sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup>

</p><p>ARCNET had the disadvantage of requiring either an active or passive hub between nodes if there were more than two nodes in the network, while thin Ethernet allowed nodes to be spaced anywhere along the linear coax cable. However, ARCNET passive hubs were very inexpensive, being composed of a simple, small, unpowered box with four ports, wired together with nothing more than four discrete resistors, so the disadvantage was not significant. This disadvantage can also be seen as an advantage: often the cost of a 4 port ARCNET passive hub was less than the 4 <a href="BNC_connector" title="BNC connector">BNC Tee</a> connectors and 2 terminators that thin Ethernet requires to connect 4 computers. Unlike BNC Tee connectors that could sometimes be hard to obtain in the early days of Ethernet, an ARCNET passive hub could be easily manufactured in the field with 9 readily available parts: 4 connectors, 4 resistors and a box to put them in.

</p><p>Passive hubs limited the distance between a node and an active hub to 30 m (100 ft). A passive hub could not be connected directly to another passive hub. Unused ports on both types of hubs had to be terminated with a special connector. This special connector, called a terminator, is just a BNC connector with a 93 ohm resistor in it. Thin Ethernet also requires nearly identical terminators at the two terminal ends, the only difference being Ethernet uses a 50 ohm resistor.

</p><p>To reduce costs while still allowing wide area coverage, a common practice was to use one or more interconnected active hubs, each of which provided coverage for nodes no more than 60 m (200 ft) away. Cable was run from each port of the active hubs to a different location no more than 30 m (100 ft) away. A passive hub would then be attached to the end of the cable, and cables would be run locally from the passive hub, allowing connection of up to three nodes. In this way, a single 8-port active hub could be used to connect 24 networked devices over an area not exceeding 120 m (400 ft) in diameter.

</p><p>ARCNET allowed only 255 nodes per network. Node IDs for LAN workstations were typically set by DIP switches on the network interface card. Larger networks would have to be split into smaller networks, and bridged. The small number of possible nodes and the need to manually configure IDs was a disadvantage compared with Ethernet, particularly as large enterprise networks became common.

</p><p>To <a href="Media_access_control" class="mw-redirect" title="Media access control">mediate access to the bus</a>, ARCNET, like Token Ring, uses a <a href="Token_passing" title="Token passing">token passing</a> scheme, rather than the <a href="Carrier_sense_multiple_access" class="mw-redirect" title="Carrier sense multiple access">carrier sense multiple access</a> approach of Ethernet. When peers are inactive, a single "token" message is passed around the network from machine to machine and no peer is allowed to use the bus unless it has the token. If a particular peer wishes to send a message, it waits to receive the token, sends its message then passes the token on to the next station. Because ARCNET is implemented as a distributed star, the token cannot be passed machine to machine around a ring. Instead, each node is assigned an 8 bit address (usually via DIP switches), and when a new node joins the network a "reconfig" occurs, wherein each node learns the address of the node immediately above it. The token is then passed directly from one node to the next.

</p><p>Historically, each approach had its advantages: ARCNET added a small delay on an inactive network as a sending station waited to receive the token, but Ethernet's original, shared-medium performance with <a href="CSMA/CD" class="mw-redirect" title="CSMA/CD">CSMA/CD</a> degraded drastically if too many peers attempted to broadcast at the same time, due to the time required for the slower processors of the day to process and recover from collisions.<sup id="cite_ref-csmacd_8-0" class="reference"><a href="#cite_note-csmacd-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> ARCNET had slightly lower best-case performance (viewed by a single stream), but was much more predictable. ARCNET also has the advantage that it achieved its best aggregate performance under the highest loading, approaching asymptotically its maximum throughput. While the best case performance was less than Ethernet, the general case was equivalent and the worst case was dramatically better. An Ethernet network could collapse when too busy due to excessive collisions. An ARCNET would keep on going at normal (or even better) throughput. Throughput on a multi-node collision-based Ethernet was limited to between 40% and 60% of bandwidth usage (depending on source). Although <span class="nowrap">2.5 Mbit/s</span> ARCNET could at one time outperform a <span class="nowrap">10 Mbit/s</span> Ethernet in a busy office on slow processors, ARCNET ultimately gave way to Ethernet as improved processor speeds reduced the impact of collisions on overall throughput, and Ethernet costs dropped.

</p><p>In the early 1980s, ARCNET was much cheaper than Ethernet, in particular for PCs. For example, in 1985 <a href="SMC_Networks" class="mw-redirect" title="SMC Networks">SMC</a> sold ARCNET cards for around <span style="white-space: nowrap">US$300</span> whilst an Ungermann-Bass Ethernet card plus transceiver could cost <span style="white-space: nowrap">US$500</span>.

</p><p>Another significant difference is that ARCNET provides the sender with a definite success/failure status of delivery at the receiver before the token passes on to the next node. This permits much faster fault recovery within the higher level protocols, rather than having to wait for a timeout on the expected replies. ARCNET also doesn't waste network time transmitting to a node not ready to receive the message, since the initial hardware-level inquiry establishes that the recipient is able and ready to receive the larger message before it is sent across the bus.

</p><p>One further advantage that ARCNET enjoyed over collision-based Ethernet is that it guarantees equitable access to the bus by everyone on the network. Although it takes a time to get the token depending on the number of nodes and the size of the messages currently being sent, a node will always receive it within a predictable maximum time. It is therefore <i>deterministic</i>. This made ARCNET an ideal <a href="Real-time_computing" title="Real-time computing">real-time</a> networking system, which explains its use in the embedded systems and process control markets. Token Ring has similar qualities, but is much more expensive to implement than ARCNET.

</p><p>In spite of ARCNET's deterministic operation and historic suitability for real-time environments such as process control, the general availability of <a href="Network_switch" title="Network switch">switched</a> <a href="Gigabit_Ethernet" title="Gigabit Ethernet">gigabit Ethernet</a> and <a href="Quality_of_service" title="Quality of service">Quality of service</a> capabilities in Ethernet switches has all but eliminated ARCNET today.

</p><p>At first the system was deployed using the RG-62/U <a href="Coaxial_cable" title="Coaxial cable">coaxial cable</a> commonly used in <a href="IBM_mainframe" title="IBM mainframe">IBM mainframe</a> environments to connect <a href="IBM_3270" title="IBM 3270">3270</a> terminals and controllers, but later added support for <a href="Twisted_pair" title="Twisted pair">twisted pair</a> and <a href="Optical_fiber" title="Optical fiber">fibre</a> media. At ARCNET's lower speeds (<span class="nowrap">2.5 Mbit/s</span>), <a href="Category_3_cable" title="Category 3 cable">Cat-3</a> cable is good enough to run ARCNET. Some ARCNET twisted-pair products supported cable runs over 2,000 ft (610 m) on standard Cat-3 cable, far beyond anything Ethernet could do on any kind of copper cable.

</p><p>In the early 1990s, <a href="Thomas-Conrad" title="Thomas-Conrad">Thomas-Conrad Corporation</a> developed a <span class="nowrap">100 Mbit/s</span> topology called TCNS based on the ARCNET protocol, which also supported RG-62, twisted-pair, and fiber optic media.<sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup> TCNS enjoyed some success until the availability of lower-cost <span class="nowrap">100 Mbit/s</span> Ethernet put an end to the general deployment of ARCNET as a LAN protocol.

</p><p>However, because of its simple and robust nature, ARCNET controllers are still sold and used in industrial, embedded, and automotive applications.

</p>

<ul><li><a href="List_of_device_bandwidths" class="mw-redirect" title="List of device bandwidths">List of device bandwidths</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFMuller2003" class="citation book cs1">Muller, Nathan J. (2003). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=uj-RtknCc_oC&pg=PA19"><i>LANs to WANs: The Complete Management Guide</i></a>. Artech House. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781580535731</bdi>.</cite></span>

</li>

<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://arcnet.cc/history.htm">"ARCNET and the ATA History"</a>. <i>arcnet.cc</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2022-10-14</span></span>.</cite></span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20030122050501/http://support.radioshack.com/support_accessories/doc22/22520.htm">"Arcnet Board Parts List"</a>. RadioShack. Archived from <a rel="nofollow" class="external text" href="http://support.radioshack.com/support_accessories/doc22/22520.htm">the original</a> on 2003-01-22.</cite></span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text"><cite id="CITEREFReed" class="citation web cs1">Reed, Matthew. <a rel="nofollow" class="external text" href="http://www.trs-80.org/arcnet/">"Tandy Picks ARCNET"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20220331111152/http://www.trs-80.org/arcnet/">Archived</a> from the original on 2022-03-31<span class="reference-accessdate">. Retrieved <span class="nowrap">2022-10-13</span></span>.</cite></span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><cite id="CITEREFReed" class="citation web cs1">Reed, Matthew. <a rel="nofollow" class="external text" href="http://www.trs-80.org/model-4p/">"The TRS‑80 Model 4P"</a><span class="reference-accessdate">. Retrieved <span class="nowrap">2022-10-13</span></span>.</cite></span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.ccontrols.com/arccontrol/index.htm">"ARC Control"</a>. <i>www.ccontrols.com</i><span class="reference-accessdate">. Retrieved <span class="nowrap">2022-10-14</span></span>.</cite></span>

</li>

<li id="cite_note-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-7">^</a></b></span> <span class="reference-text">IEEE 802.3 Clause 10.1.1.1</span>

</li>

<li id="cite_note-csmacd-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-csmacd_8-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFCarleton_University" class="citation web cs1">Carleton University. <a rel="nofollow" class="external text" href="http://www.sce.carleton.ca/faculty/lambadaris/courses/462/csma_cd.pdf">"Efficiency of CSMA/CD"</a> <span class="cs1-format">(PDF)</span>.</cite></span>

</li>

<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="https://archive.org/stream/ARCNET-DocumentManagement/ARCNET-DocumentManagement_djvu.txt">"The Rodney Dangerfield of Network Computing"</a>, archive.org</span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li><a rel="nofollow" class="external text" href="https://www.arcnet.cc/resources/ata8781.pdf">ARCNET standard ATA 878.1-1999</a></li>

<li>RFC <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1201">1201</a> Transmitting IP Traffic over ARCNET Networks</li>

<li><a rel="nofollow" class="external text" href="http://www.arcnet.cc/">ARCNET Resource Center</a></li>

<li><a rel="nofollow" class="external text" href="http://www.sohard.de">SOHARD Embedded Systems GmbH</a> - European Producer of ARCNET-Products</li>

<li><a rel="nofollow" class="external text" href="http://www.fundinguniverse.com/company-histories/Datapoint-Corporation-Company-History.html">History of Datapoint, including ARCnet / ARCnet Plus Development</a></li></ul></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-08-01" href="https://en.wikipedia.org/wiki/?title=ARCNET&oldid=1303619166">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>